Handover of a mobile terminal in a multi-beam satellite based on network conditions

ABSTRACT

Methods and systems are described for providing satellite beam handover based on predicted network conditions. In embodiments, a satellite communications system retrieves flight plan data for a plurality of aircraft being provided a network access service, identifies, for each aircraft respective candidate satellite beams of the plurality of satellite beams for providing the network access service, each candidate satellite beam having an associated service timeframe for providing the network access service, obtains, for each of the respective candidate satellite beams, a beam utilization score indicative of predicted beam utilization by the plurality of aircraft over the associated service timeframe, selects satellite beams for providing the network access service of each aircraft of the plurality of aircraft based at least in part on the beam utilization scores, and schedules handover of the network access service for the plurality of aircraft to the selected satellite beams.

CROSS REFERENCE

The present Application for Patent is a Continuation of U.S. patentapplication Ser. No. 16/847,507 by TREESH, entitled “Handover Based onPredicted Network Conditions” filed Apr. 13, 2020, which is aContinuation of U.S. patent application Ser. No. 16/368,307 by TREESH,entitled “Handover Based on Predicted Network Conditions” filed Mar. 28,2019, which is a Continuation of U.S. patent application Ser. No.15/666,257 by TREESH, entitled “Handover Based On Predicted NetworkConditions,” filed Aug. 1, 2017, each of which is assigned to theassignee hereof and expressly incorporated by reference herein in itsentirety.

BACKGROUND

The present disclosure relates to wireless communications in general,and in particular, to satellite beam handover based on predicted networkconditions.

Increasingly, passengers on commercial aircraft desire broadband networkaccess while in-flight. Passenger aircraft may receive network accessservice via a shared communication link such as a satellitecommunications link. The aircraft may have an on-board multi-user accessterminal that communicates with ground stations (e.g., via a satelliteof a satellite communications system) and provides network accessconnectivity for the passengers. For example, users may connect theircommunication devices (e.g., smartphones, laptops, tablets, etc.) to awireless local area network (WLAN) served by the multi-user accessterminal, which routes data communications to other networks (e.g., theInternet) via the shared communication link. The satellitecommunications system may be a multi-beam satellite system and theshared communication link may use resources of a satellite beam for theshared communication link. While the resources of each satellite beammay be flexibly applied, each aircraft may represent a large number ofusers, all potentially accessing broadband content concurrently.Increasing bandwidth for wireless communications systems is expensiveand sometimes additional usable spectrum is unavailable. An aircraftwithin the coverage area of a satellite beam may have a large impact onthe utilization of network resources within the beam, and in someinstances particular beams of a satellite system may becomeover-utilized.

SUMMARY

Methods, systems, and devices for predictive satellite beam handoverbased on network conditions are described. As demand for network servicefrom fixed terminals and mobile users on aircraft compete for limitedsystem resources, satellite communications systems may utilizetechniques to better distribute scarce network resources. Thesetechniques may allow for optimized use of network resources for aircraftin service areas or service periods where greater network demand isexpected.

A beam handover manager may enhance efficiency of use of networkresources of a satellite system over a service timeframe employing thedescribed techniques. Based on flight plan data for a plurality ofaircraft, the beam handover manager determines a candidate set ofsatellite beams of the satellite system to provide network accessservice to aircraft over the service timeframe. A beam utilizationscore, which indicates predicted beam utilization for each satellitebeam, is calculated for each satellite beam over the service timeframe.The beam handover manager then determines whether the beam utilizationscore for each satellite beam meets a beam utilization criteria over theservice timeframe. If the criteria is met, the beam handover manager mayaccept the candidate set of satellite beams as satisfactorily being ableto provide network access service to the aircraft over the servicetimeframe. The beam handover manager then schedules handovers for theaircraft based on the respective candidate sets of satellite beams.However, if the criteria is not met, the beam handover manager mayutilize a variety of techniques to adjust the candidate sets ofsatellite beams in order to have the beam utilization scores for thesatellite beams meet the beam utilization criteria.

BRIEF DESCRIPTION OF THE DRAWINGS

A further understanding of the nature and advantages of embodiments ofthe present disclosure may be realized by reference to the followingdrawings. In the appended figures, similar components or features mayhave the same reference label. Further, various components of the sametype may be distinguished by following the reference label by a dash anda second label that distinguishes among the similar components. If onlythe first reference label is used in the specification, the descriptionis applicable to any one of the similar components having the same firstreference label irrespective of the second reference label.

FIG. 1 is a simplified diagram of a satellite communications system inwhich the principles included herein may be described.

FIG. 2 is a diagram showing an example of a service area with asatellite providing network coverage with satellite beams in accordancewith various aspects of the present disclosure.

FIG. 3 illustrates service availabilities depicting determination ofcandidate satellite beams for aircraft based on flight plan data, inaccordance with various aspects of the present disclosure.

FIG. 4A illustrates an example of a chart of estimated beam utilizationof satellite beams by various fixed terminals, in accordance withvarious aspects of the present disclosure.

FIGS. 4B, 4C, and 4D illustrate a series of charts of expected beamresource utilization showing optimization iterations of assigningaircraft to candidate satellite beams over the service timeframe, inaccordance with various aspects of the present disclosure.

FIG. 5 is a block diagram illustrating an example of a ranked list of aplurality of aircraft based on a beam flexibility metric, in accordancewith various aspects of the present disclosure.

FIG. 6 is a flowchart diagram for managing satellite beam handover basedon predicted network conditions, in accordance with various aspects ofthe present disclosure.

FIG. 7 is a block diagram illustrating an example of a beam handovermanager for satellite beam handover based on predicted networkconditions, in accordance with various aspects of the presentdisclosure.

FIG. 8 is a block diagram illustrating an example of a gateway forsatellite beam handover based on predicted network conditions, inaccordance with various aspects of the present disclosure.

FIGS. 9 and 10 are flowchart diagrams of example methods for performingsatellite beam handover based on predicted network conditions.

DETAILED DESCRIPTION

The described features relate to satellite beam handover based onpredicted network conditions. The described handover techniques may useflight plan data to identify candidate satellite beams for providingnetwork service for a plurality of aircraft. Each of the candidatesatellite beams may be available for providing the network service overa particular service timeframe based on the beam coverage areas and theflight plan data. The techniques may then obtain a beam utilizationscore for each of the candidate satellite beams, the score indicatingthe predicted beam utilization of the candidate satellite beam over anassociated service timeframe. The techniques allow for a satellitecommunications system to select satellite beams for providing networkservice of each aircraft based on the candidate satellite beams' beamutilization scores. After the satellite beams are selected, the systemmay then schedule handovers or a series of handovers of network servicefor the aircraft to the selected satellite beams.

This description provides examples, and is not intended to limit thescope, applicability or configuration of embodiments of the principlesdescribed herein. Rather, the ensuing description will provide thoseskilled in the art with an enabling description for implementingembodiments of the principles described herein. Various changes may bemade in the function and arrangement of elements.

Thus, various embodiments may omit, substitute, or add variousprocedures or components as appropriate. For instance, it should beappreciated that the methods may be performed in an order different thanthat described, and that various steps may be added, omitted orcombined. Also, aspects and elements described with respect to certainembodiments may be combined in various other embodiments. It should alsobe appreciated that the following systems, methods, devices, andsoftware may individually or collectively be components of a largersystem, wherein other procedures may take precedence over or otherwisemodify their application.

FIG. 1 is a simplified diagram of a satellite communications system 100in which the principles included herein may be described. The satellitecommunications system 100 may provide network access service to users180 on-board mobile vessels 130-a. The network access service may beprovided to the users 180 via a multi-user access terminal 170, to whichusers 180 may connect their communication devices 175 via wired (e.g.,Ethernet) or wireless (e.g., WLAN) connections 176. The multi-useraccess terminal 170 may obtain the network access service via asatellite beam 145. The satellite communications system 100 is amultiple access system capable of providing network service for multiplemobile vessels 130 (e.g., mobile vessels 130-a, 130-n, etc.) and thenetwork users 180 of each mobile vessels 130. It should be noted thatalthough mobile vessels 130-a through 130-n are illustrated as aircraftand aircraft are used as examples in the description that follows,references to aircraft may also be any type of mobile vesseltransporting multiple passengers such as buses, trains, ships, etc.

The satellite communications system 100 may include any suitable type ofsatellite system, including a geostationary satellite system, mediumearth orbit (MEO), or low earth orbit (LEO) satellite system. Althoughonly a single satellite beam 145 is illustrated, the satellite 105 maybe a multi-beam satellite, transmitting a number (e.g., typically20-500, etc.) of satellite beams 145 each directed at a different regionof the earth. The satellite beams 145 of satellite 105 may includesatellite beams that may be of different sizes from each other. Thenumber of satellite beams 145 can allow coverage of a relatively largegeographical area and frequency re-use within the covered area.Frequency re-use in multi-beam satellite systems permits an increase incapacity of the system for a given system bandwidth. Althoughillustrated as including one satellite 105, the satellite communicationssystem 100 may include multiple satellites. The multiple satellites mayhave service coverage areas that at least partially overlap with eachother.

The satellite communications system 100 includes a gateway system 115and a network 120, which may be connected together via one or more wiredor wireless links. The gateway system 115 is configured to communicatewith one or more aircraft 130 via satellite 105. The network 120 mayinclude any suitable public or private networks and may be connected toother communications networks (not shown) such as the Internet,telephony networks (e.g., Public Switched Telephone Network (PSTN),etc.), and the like. The network 120 may connect the gateway system 115with other gateway systems, which may also be in communication with thesatellite 105. Alternatively, a separate network linking gateways andother nodes may be employed to cooperatively service user traffic.Gateway system 115 may also be configured to receive return link signalsfrom fixed terminals 185 and aircraft 130 (via the satellite 105) thatare directed to a destination in the network 120 or the othercommunication networks.

The gateway system 115 may be a device or system that provides aninterface between the network 120 and the satellite 105. The gatewaysystem 115 may use an antenna 110 to transmit signals to and receivesignals from the satellite 105 via a gateway uplink 135 and a gatewaydownlink 140. The antenna 110 may be two-way capable and designed withadequate transmit power and receive sensitivity to communicate reliablywith the satellite 105. In one embodiment, satellite 105 is configuredto receive signals from the antenna 110 within a specified frequencyband and specific polarization.

The satellite communications system 100 also includes a beam handovermanager 125, which may be coupled with gateway system 115 and/or network120. The beam handover manager 125 may receive flight plan data foraircraft 130 that are being provided network access service by satellitecommunications system 100. The beam handover manager 125 may receiveflight plan data for aircraft 130 that are already in flight at the timethe flight plan data is initially received or updated, or for aircraftthat are not yet in flight but have filed a flight plan or otherwisehave a planned flight path. For example, the flight plan data may bereceived for each of multiple aircraft 130, from a centralized databaseaccessible via network 120, etc. The centralized database may include,for example, filed flight plan information (e.g., flight paths filedwith the Federal Aviation Administration (FAA), etc.), and may besupplemented with current status information (e.g., takeoff information,GPS coordinates, flight delays, etc.). The flight plan data may includepresent route information, planned route information, or other pathrelated information associated with the aircraft 130. For example,planned information can include origin and destination locations, andplanned travel path, altitude, speed, etc. over the trip. Presentinformation can include present (or last reported) location, altitude,speed, etc. Other path related information may include weather patternsor historical data from similar trips.

The beam handover manager 125 may use the received flight plan data toidentify candidate satellite beams for providing network service tomobile multi-user terminals on multiple aircraft 130 over a servicetimeframe, which may be the time over which the flight plan data isknown, or some other time interval. Each of the candidate satellitebeams may be available for providing the network service to differentaircraft over different service windows. The flight plan data mayinclude predicted flight route information, or other information (e.g.,departure location, destination location, departure time, estimatedarrival time, etc.) from which a flight path may be estimated for theaircraft.

Beam handover manager 125 may then then obtain a beam utilization scorefor each of the candidate satellite beams, the score indicating thepredicted beam utilization of the candidate satellite beam over anassociated service timeframe. The predicted beam utilization of acandidate satellite beam may be based on the predicted network demandsfor any multi-user access terminals 170 and/or fixed terminals 185 to beserviced by the candidate satellite beam within the associated servicetimeframe. Beam handover manager 125 may then select satellite beams forproviding network service of each aircraft based on the satellite beams'beam utilization scores. After the satellite beams are selected, beamhandover manager 125 may then schedule handovers or a series ofhandovers of network service for the aircraft 130 to the selectedsatellite beams. The manner in which the beam handover manager 125schedules the handover(s) to the selected satellite beam(s) for eachaircraft 130 can vary from embodiment to embodiment. In someembodiments, the beam handover manager 125 schedules the handover(s) bystoring data in memory indicating each of the selected satellite beam(s)and the time to handover to each. When is it time for handover, the beamhandover manager 125 can then notify the aircraft 130 by communicating amessage via the satellite communications system 100 to the correspondingmulti-user access terminal 170 indicating the selected satellite beam.The message may include a unique identifier of the multi-user accessterminal 170 and/or aircraft 130 that can be used to determine themessage is intended for it. In response to the message, the multi-useraccess terminal 170 can then handover communications to the selectedsatellite beam. Handover of communications to the selected satellitebeam may, for example, include changing one or more parameters of themulti-user access terminal 170 such as the operating frequencies,polarization, power level, etc. In embodiments in which the handoverincludes switching communication to a second satellite, this may alsoinclude repointing of the antenna 165 at the second satellite.

In other embodiments, the beam handover manager 125 schedules thehandover(s) by communicating a respective message to each aircraft 130indicating some or all of the selected satellite beam(s) and the time tohandover to each. The multi-user access terminal 170 of each aircraft130 can store its respective message in memory. When it is time forhandover, the multi-user access terminal 170 can then handovercommunications to the selected satellite beam.

Each satellite beam 145 of the satellite 105 may support the aircraft130 within its coverage area (e.g., providing uplink and downlinkresources). The coverage of different satellite beams 145 may benon-overlapping or have varying measures of overlap. Satellite beams 145of the satellite 105 may be tiled and partially overlapping to providecomplete or almost complete coverage for a relatively large geographicalarea where partially overlapping (e.g., at a beam contour defined by abeam strength or gain for providing service via the beam) beams usedifferent ranges of frequencies and/or polarizations (e.g., differentcolors). Some satellite beams 145 may be sized differently (have adifferent beamwidth) than other satellite beams 145. For example, thecoverage area of one satellite beam may be partially overlapping orlocated entirely within a different satellite beam. Some satellite beams145 may be targeted at areas of higher demand (e.g., more denselypopulated areas), while other satellite beams 145 provide service overlarger areas. Thus, an aircraft 130 at any given location may be able tobe served by one of multiple available satellite beams, which may besatellite beams of the same satellite, or different satellites, in somecases.

The multi-user access terminal 170 may use an antenna 165 mounted onaircraft 130-a to communicate signals with the satellite 105 via asatellite beam downlink 155-a and satellite beam uplink 160-a. Theantenna 165 may be mounted to an elevation and azimuth gimbal whichpoints the antenna 165 (e.g., actively tracking) at satellite 105. Thesatellite communications system 100 may operate in the InternationalTelecommunications Union (ITU) Ku, K, or Ka-bands, for example from 17.7to 21.2 Giga-Hertz (GHz) in the downlink portion and from 27.5 to 31 GHzin the uplink portion of the Ka band. Alternatively, satellitecommunications system 100 may operate in other frequency bands such asC-band, X-band, S-band, L-band, and the like.

In satellite communication system 100, users 180-a to 180-n may utilizethe network access service via mobile devices 175. Each user 180-a to180-n may be provided service via the satellite communication system 100by connecting (e.g., via a wired or wireless connection) a mobile device175 (e.g., desktop computer, laptop, set-top box, smartphone, tablet,Internet-enabled television, and the like) to the multi-user accessterminal 170. As illustrated in FIG. 1 , mobile devices 175-a to 175-nare connected via wired or wireless connections 176 (e.g., Wi-Fi,Ethernet, etc.) to multi-user access terminal 170. Multi-user accessterminal 170 may receive data from satellite 105 via satellite beamdownlink 155-a and transmit data to satellite 105 via satellite beamuplink 160-a. Other aircraft within the satellite beam 145 such asaircraft 130-n may receive data from satellite 105 via satellite beamdownlink 155-n and transmit data to satellite 105 via satellite beamuplink 160-n. While satellite communication system 100 is illustratedproviding mobile network access service to mobile users 180 aboardaircraft 130, it can be appreciated that the principles described hereinfor providing network access service to mobile users may be providedusing multi-user access terminals positioned in fixed locations or onvarious modes of transportation where multiple mobile users may desirenetwork access via satellite communications system 100 (e.g., trains,boats, busses, etc.).

Each satellite beam 145 of the satellite 105 may also support a numberof fixed terminals 185. Fixed terminals 185 may receive data fromsatellite 105 via satellite beam downlink 155-b and transmit data viasatellite beam uplink 160-b. A fixed terminal 185 may be any two-waysatellite ground station such as a very small aperture terminal (VSAT).A fixed terminal 185 may provide services to subscribers associated withthe fixed terminal such as data, voice, and video signals. Each fixedterminal may typically provide service to a small number of users (e.g.,a residence or business). As illustrated in FIG. 1 , a satellite beam145, assigned to a particular frequency range and polarization, maycarry satellite beam downlinks 155 or satellite beam uplinks 160 forboth fixed terminals 185 and multi-user access terminals 170. Thesatellite beam downlinks 155 or satellite beam uplinks 160 for fixedterminals 185 and multi-user access terminals 170 may be multiplexedwithin the satellite beam 145 using multiplexing techniques such astime-division multiple access (TDMA), frequency-division multiple access(FDMA), multi-frequency time-division multiple access (MF-TDMA),code-division multiple access (CDMA), orthogonal frequency divisionmultiple access (OFDMA), and the like.

FIG. 2 is a diagram showing an example of a service area 200 withsatellite 105-a providing network coverage with satellite beams inaccordance with various aspects of the present disclosure. The satellite105-a may use a particular system bandwidth and have multiple satellitebeams 205-a, 205-b, 205-c, and 205-d (shown by their associatedsatellite beam coverage areas). The satellite beams 205 may each useportions of the system resources (e.g., a polarization and a portion ofthe system bandwidth, etc.). The satellite beam coverage areas mayillustrate a given beam contour level of the corresponding satellitebeam associated with a minimum desired signal level for service via thesatellite beam. For example, the satellite beam coverage areas mayrepresent a −1 dB, −2 dB, or −3 dB attenuation from the peak gain, ormay be defined by an absolute signal strength, signal-to-noise ratio(SNR), or signal-to-interference plus noise ratio (SINR) level. Thesatellite beam coverage areas for satellite beams 205 may be differentsizes and/or dimensions for various reasons such as satellite azimuth,frequency, or intentional beam-shaping techniques (e.g., shaped antennasystems, beamforming, etc.). Each satellite beam 205 may service one ormore aircraft within its satellite beam coverage area, and aircraftwithin more than one satellite beam 205 may be serviced by any one ofthe satellite beams at a given time.

The illustrated service area 200 may be a region within an overallservice area of satellite 105-a and may include other satellite beamsthat are not shown in FIG. 2 for the sake of clarity. Satellite 105-amay be a part of various types of satellite systems. For example,satellite 105-a may utilize a fixed beam architecture where thesatellite beams may each be intentionally fixed on particular geographicareas. A fixed beam refers to a spot beam for which the angularbeamwidth and coverage area does not intentionally vary with time.Geostationary satellites often use fixed beams. In some examples,satellite beam coverage areas of adjacent satellite beams in a fixedbeam system may be partially overlapping to provide continuous coverage,and overlapping satellite beams use different ranges of frequenciesand/or polarizations (e.g., colors). In other examples, satellite 105-amay be part of a Low Earth Orbit (LEO) satellite system. To maintain astable low Earth orbit, a satellite in a LEO satellite system needs tosustain a minimum orbital velocity which may not be the same speed atwhich the Earth rotates. Because a particular satellite's orbit is notgeostationary, satellite 105-a may be a network of satellites in orderto provide continuous coverage over service area 200. The network ofsatellites may move following a similar orbit path in order to providecontinuous network service to service area 200.

FIG. 2 shows the flight plans for multiple aircraft 130 flying orscheduled to fly through the service area 200 within a servicetimeframe. For example, aircraft 130-a, 130-b, and 130-c may betraveling or are forecasted to travel through satellite beams 205-a,205-b, 205-c, and 205-d. Beam handover manager 125 may determine theforecasted travel paths for each of aircraft 130 through flight plandata that beam handover manager 125 receives for each aircraft 130.

From the current geographic locations and forecasted travel paths ofeach aircraft 130, beam handover manager 125 may determine the predictedlocations of each aircraft 130 during a service timeframe (e.g., apredetermined period of time or a time period for which flight data isknown, etc.). Based on the predicted locations, beam handover manager125 may identify prospective candidate satellite beams that may be ableto provide network access service to each aircraft 130 within theservice timeframe. Each prospective candidate satellite beam may have anassociated service window for each aircraft 130 for which it can providenetwork service during the service timeframe.

FIG. 3 illustrates service availabilities 300-a, 300-b, 300-c, and 300-ddepicting determination of candidate satellite beams for aircraft basedon flight plan data, in accordance with various aspects of the presentdisclosure. For example, FIG. 3 may illustrate when satellite beams205-a, 205-b, 205-c, and 205-d may provide network service to aircraft130-a, 130-b, and 130-c of FIG. 2 over service timeframe 305. Servicetimeframe 305 may be a fixed period of time (e.g., a given number ofminutes or hours, etc.), or may be dynamically determined based on theavailability of flight data or estimated accuracy of flight data overtime.

Specifically, service availability 300-a illustrates service windowst_(SW)[A:1] 310-a-1, t_(SW)[B:1] 310-b-1, and t_(SW)[C:1] 310-c-1 whensatellite beam 205-a of FIG. 2 is a candidate beam for aircraft 130-a,130-b, and 130-c, respectively. As can be seen from FIG. 2 , aircraft130-b begins its flight plan within the coverage area of satellite beam205-a, which is shown in FIG. 3 by service window t_(SW)[B:1] 310-b-1starting at the beginning of service timeframe 305. The flight plan datafor aircraft 130-a and 130-c show them to be outside the coverage areafor satellite beam 205-a at the beginning of the service timeframe 305(which may be the current time). Thus, service windows t_(SW)[A:1]310-a-1 and t_(SW)[C:1] 310-c-1 do not start at the beginning of theservice timeframe 305. FIG. 2 illustrates aircraft 130-b and 130-cexiting the coverage area of satellite beam 205-a prior to the end ofthe service timeframe 305, which is depicted in FIG. 3 by servicewindows t_(SW)[B:1] 310-b-1 and t_(SW)[C:1] 310-c-1, respectively,terminating before the end of service timeframe 305. However, as shownby service window 310-a-1, once within the coverage area of satellitebeam 205-a, aircraft 130-a does not exit the coverage area of satellitebeam 205-a prior to the end of service timeframe 305.

In another example, service availability 300-b for satellite beam 205-bfrom FIG. 2 also shows that satellite beam 205-b provides networkservice to aircraft 130-a, 130-b, and 130-c at different times and fordifferent durations. In service availability 300-b, the service windowst_(SW)[A:2] 310-a-2, t_(SW)[B:2] 310-b-2, and t_(SW)[C:2] 310-c-2 showthe time periods that satellite beam 205-b is a candidate beam forproviding service to aircraft 130-a, 130-b, and 130-c, respectively. Ascan be seen in FIG. 2 , aircraft 130-a, 130-b, and 130-c all begin theirflight paths in coverage areas of satellite beams other than satellitebeam 205-b. This is illustrated in FIG. 3 where no service windowscommence at the beginning of service timeframe 305. Additionally,aircraft 130-a, 130-b, and 130-c end their flight paths outside thecoverage area of satellite 205-b in FIG. 2 . This is shown in FIG. 3where service windows t_(SW)[A:2] 310-a-2, t_(SW)[B:2] 310-b-2, andt_(SW)[C:2] 310-c-2 terminate before the end of service timeframe 305.

In similar examples, service availabilities 300-c and 300-d show theservice windows 310 for which satellite beams 205-c and 205-d arecandidate beams for aircraft 130-a, 130-b, and 130-c. Specifically,satellite beam 205-c is a candidate beam for aircraft 130-a, 130-c, and130-d over service windows t_(SW)[A:3] 310-a-3, t_(SW)[B:3] 310-b-3, andt_(SW)[C:3] 310-c-3, respectively, and satellite beam 205-d is acandidate beam for aircraft 130-a, 130-c, and 130-d over service windowst_(SW)[A:4] 310-a-4, t_(SW)[B:4] 310-b-4, and t_(SW)[C:4] 310-c-4,respectively.

Thus, beam handover manager 125 may determine, for each aircraft 130being provided service, service windows associated with each beamavailable to service the aircraft within the service timeframe 305. Inaddition, each of satellite beams 205 may provide service to a number offixed terminals. Beam utilization due to service of fixed terminals mayalso be estimated over the service timeframe 305.

FIG. 4A illustrates an example of a chart 400 of estimated beamutilization of satellite beams by various fixed terminals, in accordancewith various aspects of the present disclosure. For example, chart 400may illustrate beam utilization for satellite beams 205-a, 205-b, 205-c,and 205-d due to fixed terminals that are provided network service bythe respective satellite beams 205. The estimated beam utilizationdepicted in chart 400 may be exclusive of the estimated network resourcedemands of any aircraft 130 that are within the coverage area ofsatellite beams 205. Since fixed terminals generally do not move fromthe coverage area of the satellite beam 205 currently servicing them,variation of network demand over the service timeframe 305 may occur dueto a number of other factors including different network resourcedemands in different times of the day, different populations served byeach satellite beam 205, etc. The estimated beam utilization overservice timeframe 305 may be estimated for each of a plurality of timesegments 415, which may be a time unit used for beam assignmentdecisions (e.g., the smallest time unit for handover decisions andscheduling, etc.).

The estimated beam utilization shown in chart 400 may be estimated basedon current demand and historical demand data. For example, the beamutilization for fixed terminals shown in chart 400 shows that the fixedterminal estimated beam utilization 420-d for satellite beam 205-d iscurrently (e.g., at the beginning of service timeframe 305) highest. Inaddition, the fixed terminal estimated beam utilizations 420-a and 420-dfor satellite beams 205-a and 205-d, respectively, are expected todecrease over the service timeframe 305, while the fixed terminalestimated beam utilization 420-c is expected to increase over theservice timeframe 305 and the fixed terminal estimated beam utilization420-b is expected to be substantially constant over the servicetimeframe 305. Chart 400 shows the fixed terminal estimated beamutilizations 420 for satellite beams 205-a, 205-b, 205-c, and 205-d on anormalized scale of 0-120, where 100 represents the maximum capacity ofeach of the satellite beams (which may be different for differentbeams).

In addition, beam handover manager 125 may determine a serviceutilization for each aircraft 130 over the service timeframe 305. Theservice utilization for each aircraft over the service timeframe 305 maybe determined based on historical service utilization data, an estimatednumber of the passengers utilizing the network access service on eachaircraft, a service level offered to the passengers utilizing thenetwork access service on each aircraft, a predicted spectral efficiencyof communication between the satellite and the aircraft for a given beam(e.g., spectral efficiency may vary based on location of the aircraftwithin a beam or atmospheric conditions, etc.), and the like.

FIGS. 4B, 4C, and 4D illustrate a series of charts of expected beamresource utilization showing optimization iterations of assigningaircraft to candidate satellite beams over the service timeframe, inaccordance with various aspects of the present disclosure. Theoptimization process may be performed by iteratively re-assigning one ormore aircraft to different satellite beams until beam utilization scoresfor the satellite beams satisfy one or more beam utilization criteria.Beam utilization scores for each satellite beam may be, for example,normalized beam utilization as shown in FIGS. 4B-4D, or may bedetermined from the estimated beam utilization in other manners (e.g.,filtered, etc.). The beam utilization criteria may include, for example,the beam utilization scores remaining below a threshold during theservice timeframe, a maximum amount of time the beam utilization scoresmay exceed the threshold in the service timeframe, a maximum differencebetween a given beam utilization score and an average of the beamutilization scores for the plurality of satellite beams over the servicetimeframe, or a variance of the beam utilization scores for theplurality of satellite beams being below a variance threshold.

The optimization may include making a provisional selection of aircraftto candidate beams, determining beam utilization based on theprovisional selection, and performing a number of iterations ofre-assigning one or more aircraft to different beams until the beamutilization criteria are met. Selection of aircraft to re-assign for theoptimization iterations may be performed according to re-assignmentselection rules including selection of aircraft with the greatest beamflexibility, random selection, and the like. For example, if a givensatellite beam does not meet one or more beam utilization criteriaduring a particular service timeframe, an aircraft for which the givensatellite beam has been provisionally selected may have its provisionalbeam assignments changed for at least a part of the service timeframe.This process may continue until all the satellite beams meet the beamutilization criteria according to the provisional assignments.Alternatively, the optimization process may involve an optimizationusing a value function to find an optimal or near optimal beamassignment solution, as discussed in more detail below. Once theoptimization process has concluded, the provisionally selected satellitebeams may be adopted by beam handover manager 125 where for each of theaircraft the satellite beams are used according to the provisionalselection. In another embodiment, the optimization process may obtainone or more satellite beam assignment sets for providing network accessservice to the aircraft. Each of the satellite beam assignment sets mayhave one or more satellite beams provisionally assigned for servicingeach of the aircraft (e.g., successively) during a service timeframe.Each satellite beam of the satellite beam assignment sets may have abeam utilization score that meets the beam utilization criteria duringthe service timeframe. That is, multiple sets of provisional selectionsmay be determined for which the beam utilization criteria are met. Insome examples, additional criteria (e.g., total number of handovers,number of handovers for a given aircraft, etc.) may be applied to selectbetween the multiple sets.

In the example charts in FIGS. 4B, 4C, and 4D, the service utilizationfor each aircraft 130 is estimated to be a constant value of 20 unitsover the service timeframe 305. However, this value is for the purposesof illustration and may not represent a typical normalized serviceutilization for one aircraft within a satellite communications system.In addition, the estimated service utilization for aircraft 130 may varyover the service timeframe 305.

The beam optimization process may be triggered by various conditions orevents. The trigger may be periodic (e.g., optimization may be performedevery time segment 415 or predetermined number of time segments 415,every service timeframe 305, etc.) or it may be location based (e.g.,optimization may be performed when an aircraft is detected within acertain distance from an edge of a satellite beam currently serving theaircraft, entering into an overlapping region of multiple satellitebeams, etc.). The trigger may also occur based on load-balancingcriteria such as a beam utilization of a satellite beam exceeding acapacity threshold, a number of aircraft serviced by a satellite beamexceeding an aircraft threshold, a number of users of a satellite beamexceeding a user threshold, a change in capacity demand for one or moresatellite beams exceeding a threshold, or a difference of beamutilization between two or more satellite beams (e.g., adjacent beams,beams within a region, etc.) exceeding a beam delta threshold. Thetrigger may also be set when there is a change in the flight plan data(e.g., aircraft entering or exiting the network), or if a service levelof the network access service to an aircraft falls below a servicethreshold.

FIG. 4B illustrates a chart of estimated beam utilization 425 ofsatellite beams 205-a, 205-b, 205-c, and 205-d. Chart 425 may depict theexpected beam resource utilization by the fixed terminals of chart 400in addition to aircraft 130 prospectively serviced by satellite beams205. Chart 425 may show the beam utilization scores 430 of satellitebeams 205 through an initial assignment of aircraft 130 to satellitebeams 205. The initial assignment of satellite beams 205 may be doneaccording to default rules. The default rules may involve providingnetwork service to an aircraft 130 by a satellite beam 205 that iscurrently providing service, or whose coverage area the aircraft 130initially starts in at the beginning of the service window. If theaircraft 130 initially begins in the coverage area of multiple satellitebeams 205, beam handover manager 125 may select a candidate satellitebeam based on which candidate satellite beam may provide the aircraft130 with the longest possible service. After the aircraft 130 leaves thecoverage area of the selected satellite beam, beam handover manager 125may choose another candidate satellite beam based on which candidatesatellite beam may provide aircraft 130 the longest possible service.Additionally or alternatively, the default rules for initial assignmentof candidate satellite beams may include other factors such as beampriority (e.g., highest capacity beams being selected first, beams fromthe same satellite given priority, etc.) or random selection. Wherebeams from the same satellite currently providing service to an aircraftare not available, the default rules may assign an aircraft to adifferent satellite for providing service. Where multiple satellites areavailable for providing service, the default rules can select thesatellite according to priority rules (e.g., satellites using the sametechnology given preference, satellites from the same operator givenpreference, satellites providing similar link performance givenpriority, etc.).

Based on the flight paths depicted in service area 200 and the defaultrules described above, the initial assignment may have satellite beam205-c initially providing network service to aircraft 130-a. Whenaircraft 130-a is predicted to leave satellite beam 205-c, the initialassignment may handover aircraft 130-a to satellite beam 205-a fornetwork service. With regards to aircraft 130-b, it may be firstprovided network service by satellite beam 205-a and then by satellitebeam 205-d when aircraft 130-b is predicted to leave the coverage areaof satellite beam 205-a. Aircraft 130-c may start receiving networkservice from satellite beam 205-d at the beginning of the servicewindow, but then is assigned to satellite beam 205-c when it ispredicted to leave the coverage area of satellite beam 205-d.

FIG. 4B shows the beam utilization scores 430-a-1, 430-b-1, 430-c-1, and430-d-1 for satellite beams 205-a, 205-b, 205-c, and 205-d,respectively, based on applying the default rules for assignment ofaircraft to satellite beams. Based on the beam utilization scores 430,beam handover manager 125 may determine whether further optimizing ofbeam assignments is performed. In the example of FIG. 4B, the beamutilization scores 430 are illustrated as a normalized (e.g., to beamcapacity) beam utilization for each time segment 415. In other examples,the beam utilization scores may be a single value. For example, a beamutilization score may be determined as an average of the beamutilization 430 over the service timeframe 305, a percentage of timethat the beam utilization 430 is above a beam utilization threshold(e.g., 80% of the beam capacity), a peak value of the beam utilization430, a weighted average of beam utilization (e.g., higher beamutilization values given exponentially more weight, values of the beamutilization closer to the current time given more weight, etc.), orcombinations of these techniques. In some examples, beam handovermanager 125 may utilize a comparative beam utilization score, where thebeam utilization scores for each satellite beam are based on adifference between the beam utilization and an average beam utilizationof all or a subset (e.g., neighboring beams, by region, etc.) of thesatellite beams 205.

In the example shown in FIG. 4B, beam handover manager 125 may determinethat satellite beam 205-d has a beam utilization score 430-d-1 thatexceeds a predetermined threshold (e.g., 80% of the beam capacity)during the service window. Beam handover manager 125 may also determinethat satellite beam 205-c also has a beam utilization score 430-c-1that, although lower than the beam utilization score for beam 205-d,exceeds the predetermined threshold. The beam utilization threshold maybe a predetermined value based on the function used to determine thebeam utilization score. Due to the determination that at least one beamhas a beam utilization score that does not meet beam utilizationcriteria, beam handover manger 125 may decide to re-select candidatesatellite beams for one or more of aircraft 130-a, 130-b, or 130-c.

Based on the determination that satellite beam 205-d has the highestbeam utilization score 430, beam handover manager 125 may identify anaircraft 130 assigned to satellite beam 205-d during at least a portionof the service timeframe 305 that can be assigned to another candidatesatellite beam. In some examples, beam handover manager 125 may utilizea ranked list of the aircraft 130 in its reassignment decision, theranked list being based on a beam flexibility metric associated witheach of the aircraft 130. The beam flexibility metric may be based onthe number of available satellite beams for each of the aircraft 130during their service timeframes. Further details of the ranked list maybe found in the description relating to FIG. 5 below.

FIG. 4C illustrates a chart 450 of estimated beam utilization ofsatellite beams 205-a, 205-b, 205-c, and 205-d after a firstoptimization iteration. Chart 450 may depict the beam utilization scores430 of satellite beams 205 after beam handover manager 125 performs afirst optimization iteration based on the determined beam utilizationscores from chart 425.

For the first optimization iteration, beam handover manager 125 mayidentify aircraft 130-b as having the highest beam flexibility metricand may identify that aircraft 130-b can be re-assigned to satellitebeam 205-b for at least a portion of the service timeframe 305. Chart450 shows the beam utilization scores 430-a-2, 430-b-2, 430-c-2, 430-d-2of candidate satellite beams 205-a, 205-b, 205-c, and 205-d,respectively, after aircraft 130-b has been re-assigned to satellitebeam 205-b from satellite beam 205-d for at least a portion of theservice timeframe 305. As can be seen, the resulting beam utilizationscore 430-d-2 of satellite beam 205-d has dropped compared to beamutilization score 430-d-1 of FIG. 4B during the service window for whichit had been assigned to serve aircraft 130-b. However, beam handovermanager 125 may now consider satellite beam 205-c as having a beamutilization score 430-c-2 that still exceeds the beam utilizationthreshold. Due to this, beam handover manger 125 may decide to re-selectcandidate satellite beams for one or more of aircraft 130-a, 130-b, or130-c.

FIG. 4D illustrates a chart 475 of beam utilization scores of satellitebeams 205-a, 205-b, 205-c, and 205-d. Chart 475 may depict the beamutilization scores of satellite beams 205 after beam handover managerperforms a second optimization iteration based on the determined beamutilization scores from chart 450. Based on the determination thatsatellite beam 205-c has the highest beam utilization score from chart450, beam handover manager 125 may identify an aircraft 130 previouslyassigned to satellite beam 205-c to another candidate satellite beam.Again, beam handover manager 125 may utilize a ranked list of theaircraft 130.

For this example, beam handover manager 125 may identify aircraft 130-cas having the highest beam flexibility metric and may identify thataircraft 130-c can be re-assigned to satellite beam 205-a for at least aportion of the service timeframe 305. As shown in FIG. 2 , satellitebeam 205-a may service aircraft 130-c even before aircraft 130-c exitsthe coverage area of satellite beam 205-d. Chart 475 shows the beamutilization scores 430-a-2, 430-b-2, 430-c-2, 430-d-2 of candidatesatellite beams 205-a, 205-b, 205-c, and 205-d, respectively, afteraircraft 130-c has been re-assigned to satellite beam 205-a for theservice window of satellite beam 205-a for aircraft 130-c. As can beseen, the resulting beam utilization score 430-c-3 of satellite beam205-c is reduced when compared to beam utilization score 430-c-2 shownin FIG. 4C and is now below the threshold throughout the servicetimeframe 305. Beam handover manager 125 may determine that theoptimization process is complete based on the beam utilization scores430 for all the satellite beams being below the beam utilizationthreshold over the service timeframe 305. If however, after the secondoptimization iteration, the beam utilization scores 430 for one or moresatellite beams do not satisfy beam utilization criteria, the beamhandover manager 125 may continue to perform additional iterations untilthe beam utilization criteria are satisfied. With the set of candidatesatellite beams for successively providing the network service toaircraft 130 determined, beam handover manager 125 may schedulehandovers of aircraft 130 during the service timeframe according to therespective sets of candidate satellite beams selected for providingservice to each aircraft 130. Although reassignment of aircraftdiscussed in the examples given in FIGS. 4B-4D is performed overcorresponding service windows (e.g., reassignment of aircraft 130-c tosatellite beam 205-a in the second optimization iteration includesreassignment over the service window t_(SW[C:1])), reassignment of anaircraft may be for a portion of a corresponding service window, in somecases.

FIG. 5 is a block diagram illustrating an example of a ranked list 500of a plurality of aircraft 130 based on a beam flexibility metric.Ranked list 500 may illustrate a list constructed by beam handovermanager 125 as shown in FIG. 1 . Ranked list 500 may include the mostflexible rank 505 (labeled “Aircraft C”), followed by rank 510 (labeled“Aircraft D”), and rank 515 (labeled “Aircraft A”). The ranked list 500ends with the least flexible rank 520 (labeled “Aircraft N”).

In the event that beam handover manager 125 optimizes beam utilizationscores for a set of candidate satellite beams, beam handover manager 125may utilize ranked list 500 for re-assigning aircraft to differentsatellite beams based on re-assignment flexibility of the aircraft. Theoptimization process was discussed in the description relating to FIGS.4B, 4C, and 4D. In some examples, the aircraft with respective candidatesatellite beams that possessed beam utilization scores that exceeded thethreshold are identified by beam handover manager 125. With theseaircraft, beam handover manager 125 may then create a ranked list 500 ofthe identified aircraft based on a beam flexibility metric associatedwith each of the identified aircraft. The beam flexibility metric may bebased on the number of available satellite beams for the each of theidentified aircraft during the associated service timeframe. Forexample, the beam flexibility metric may be determined based on anaggregate (e.g., median, average, etc.) of the number of beams availablefor each time segment 415, or the number of time segments having atleast a certain number (e.g., two or more) available beams. In someexamples, the beam flexibility metric is determined based on a set oftime segments for which beam utilization of one or more candidate beamsexceeds a threshold.

In FIG. 5 , at least four aircraft have respective candidate satellitebeams that possess beam utilization scores that exceed thethreshold—aircraft A, aircraft C, aircraft D, and aircraft N. Beamhandover manager 125 may then rank each aircraft based on their beamflexibility metric. Upon evaluating the aircraft's respective metrics,beam handover manager 125 ranks Aircraft C as being the most flexible(i.e., the most suitable to reassign a candidate satellite beam), whileAircraft N is the least flexible. In a circumstance where candidatesatellite beams must be re-selected for one or more aircraft, beamhandover manager 125 may begin the re-selection process with Aircraft Cbecause it has the most flexibility for beam reassignment in ranked list500. In some examples, beam handover manager 125 may factor inadditional considerations in creating ranked list 500, including numberof handovers for each aircraft. Thus, beam handover manager 500 maychoose to bypass reselecting a candidate satellite beam for Aircraft Cbecause a re-selection scenario involving a lower ranked aircraft mayprovide for a better outcome. Beam handover manager 125 may choose oneor more aircraft from the ranked list in order to perform thereselection process.

FIG. 6 is a flowchart diagram of an example method 600 for managingsatellite beam handover based on predicted network conditions. Method600 may be performed, for example, by the beam handover manager 125 ofFIGS. 1, 7, and 8 for a satellite communications system 100 servicing anumber of aircraft and fixed terminals via one or more multi-beamsatellites. The method 600 begins at a trigger 602, which may be atriggering event or condition as described above.

At block 605, beam handover manager 125 may determine an initialassignment of aircraft to candidate satellite beams over a servicetimeframe. The service timeframe may begin at the time at which theoptimization process is triggered (e.g., the current time of theoptimization), and extend over a time period that may be predeterminedor may be dynamically determined based on availability or predictedaccuracy of flight plan data for aircraft served by the satellitecommunications system. The candidate satellite beams may be satellitebeams 205 of one or more multi-beam satellites that may provide networkaccess service to aircraft 130 within the service area of the satellitecommunications system. The satellite beams 205 may also provide networkaccess service to a number of fixed terminals within the service area.The initial assignment of satellite beams 205 may be done according todefault rules as described above.

Beam handover manager 125 may then perform a beam selection optimizationsub-process 650. Beam selection optimization sub-process 650 may be usedto traverse a search tree, where each beam selection node on the treemay be understood as a set of beam assignments for successively (e.g.,continuously or as close as is possible given satellite beam coverage,etc.) providing service to each aircraft over the service timeframe.

At block 610 of beam utilization optimization sub-process 650, beamhandover manager 125 determines beam utilization scores for eachcandidate satellite beam based on the current set of beam assignments(e.g., the initial assignments for the first optimization pass). Forexample, the beam handover manager 125 may determine the beamutilization for each beam over the service timeframe, and the beamutilization scores may be determined as a function of the beamutilization (e.g., average, weighted average, peak beam utilization,time beam utilization is above a threshold, filtered, normalized, etc.)over the service timeframe. Additionally, beam handover manager 125 mayconsider other optimization metrics. For example, beam handover manager125 may assign an optimization cost to handovers encountered by anaircraft 130. Because a satellite beam handover of an aircraft frombeing served by one satellite beam to another is accompanied by the useof a certain amount of system resources and overhead, increases in thenumber of handovers may actually decrease overall system performance. Inaddition, handovers may cause temporary service disruption for usersthat may impact the user experience. Thus, the optimization cost forhandovers may take into account the overall cost of handovers to systemperformance and user experience impact.

At block 615, beam handover manager 125 evaluates the beam utilizationscore for each candidate satellite beam. The evaluation may involve beamhandover manager 125 determining if the beam utilization scores satisfya beam utilization criteria. The beam utilization criteria may vary fromembodiment to embodiment. For example, the beam utilization criteria mayinvolve the beam utilization scores of every satellite beam being belowa threshold. In another example, the criteria may involve a relativemetric for the beam utilization scores (e.g., a differential betweenneighboring beams or beams within a region to be below a threshold,etc.). Additionally, the provisional selections may also be evaluatedaccording to handover criteria. For example, solutions may beprioritized based on a total number of handovers of the aircraft 130being served by the satellite communications system (e.g., preference isgiven to solutions achieving the beam utilization criteria with a lowertotal number of handovers, etc.). Additionally or alternatively, thehandover criteria may include a maximum number of handovers or a minimumtime between handovers for a given aircraft within the servicetimeframe, or give priority to solutions having a lower maximum numberof handovers for any one aircraft 130. In addition, the criteria mayinclude aircraft location criteria such as predicted location ofaircraft within the satellite beams within the service timeframe. Forexample, solutions with fewer aircraft towards the edge of satellitebeams for longer periods of time may be ranked higher than solutionswith more aircraft in beam edge regions. In some examples, satellitebeams may have cost metrics assigned based on a cost to utilize thebeams, and the criteria may account for the cost metrics in evaluationof solutions.

At decision block 620, beam handover manager 125 determines if the setof candidate satellite beams is able to provide network access serviceto aircraft 130 while meeting the beam utilization criteria. If the setof candidate satellite beams meets the beam utilization criteria, thenmethod 600 proceeds to block 630 where beam handover manager 125schedules the handover of aircraft 130 to their respective determinedcandidate satellite beams for the future service window. If the set ofcandidate satellite beams does not meet the beam utilization criteria,the method proceeds to block 625.

At block 625, beam handover manager 125 re-assigns one or more aircraftto different candidate satellite beams for at least a portion of theservice timeframe in order to optimize the beam utilization scores ofthe satellite beams. Beam handover manager 125 may utilize a variety ofoptimization techniques that may vary from embodiment to embodiment. Forexample, beam handover manager 125 may randomly assign one or moreaircraft 130 to different candidate satellite beams than they arecurrently assigned. In another example, beam handover manager 125 maychoose the candidate satellite beam possessing the highest beamutilization score and re-assign or one or more aircraft 130 served bythat beam during the service timeframe to a different beam. Indetermining the one or more aircraft 130 to assign to differentcandidate satellite beams, beam handover manager 125 may utilize aranked list of the one or more aircraft 130 based on each aircraft'sbeam flexibility metric as discussed above. In yet another technique,beam handover manager 125 may re-assign candidate satellite beams oraircraft 130 based on re-assignments that minimize handovers. Thus ifre-assigning fewer aircraft, or performing re-assignments that do notincrease the number of handovers is an option, beam handover manager 125may prioritize that consideration over other factors during theoptimization process.

Upon re-assigning the set of candidate satellite beams in block 625,method 600 reverts back to block 610 where beam handover manager 125assigns a beam utilization score to each candidate satellite beam asdescribed above. After evaluating the beam utilization scores at block615, beam handover manager 125 again determines if the optimized set ofcandidate satellite beams will provide network service to each aircraftwhile meeting the beam utilization criteria. If it will not, method 600proceeds to block 625 for another optimization iteration. If it will,method 600 ends at block 630 with beam handover manager 125 schedulingthe handovers associated with the optimized set of beam assignments.

As described for blocks 610, 615, 620 and 625, the beam selectionoptimization sub-process 650 is performed using beam re-assignment rulesat block 625 (e.g., rules for re-assigning aircraft to different beams)and beam utilization criteria at block 620 for determining the finalbeam assignments. Techniques using iterative re-assignment that startfrom an initial assignment (e.g., based on default rules or currentassignments, etc.) and then stop searching once the criteria (e.g., beamutilization criteria, handover criteria, aircraft location criteria,etc.) are met may find a solution that meets the criteria with a minimumnumber of changes to the current assignments. However, these techniquesmay also fail to find a solution meeting the criteria, or find asolution that is sub-optimal over the entire solution space. Otheroptimization techniques may also be used in addition or as analternative for finding optimal or near-optimal beam assignmentsolutions. For example, if the beam utilization optimization sub-process650 fails to find a solution in a given number of iterations using beamre-assignment according to beam flexibility metrics, techniques such asa random re-assignment of one or more aircraft to different beams may beemployed to provide a wider scope of solutions sets.

Optimization techniques for finding optimal or near-optimal solutionsmay optimize a value function that takes into account the beamutilization scores for the candidate satellite beams and otheroptimization metrics. For example, the value function may incorporatethe beam utilization scores (e.g., evaluated for the effect of beamutilization to service impact, etc.), beam utilization over the servicetimeframe, number and/or frequency of handovers, and cost of utilizationof particular beams as cost metrics of the value function. The valuefunction may take into account predicted service utilization of eachaircraft as it traverses each candidate beam. For example, the expecteddata rate over the service timeframe may be estimated for each aircraft,and the service utilization may take into account an expected spectralefficiency of communication between the satellite and the aircraft as ittraverses a given beam (e.g., spectral efficiency may be higher at thecenter of the beam or may be impacted by predicted atmosphericconditions).

In some examples, Monte Carlo tree search may be used to traverse beamselection paths between beam selection nodes. The Monte Carlo treesearch may use random or semi-random expansion rules to choose childbeam selection nodes from a given beam selection node, and may useback-propagation to expand from different beam selection nodes based onthe updated beam utilization scores at each beam selection node.Additionally or alternatively, branch and bound techniques for pruningthe search tree of beam selection nodes may be used including minimaxpruning, naïve minimax pruning, or alpha-beta pruning.

In some examples, beam optimization sub-process 650 may usecombinatorial optimization techniques such as dynamic programming tocompute the optimal or near-optimal (e.g., based on maximizing the valuefunction) beam selection for each aircraft over the service timeframe.In one example, the assignment of aircraft within the satellitecommunications system may be modeled as a generalized assignment problemwith knapsack constraints (e.g., applying system constraints such asbeam bandwidth, etc.). The dynamic programming techniques may evaluatemultiple beam assignment hypotheses over the service timeframe todetermine the optimal or near optimal beam assignments according to thevalue function. In some examples, approximate programming techniques maybe used to reduce computational complexity. For example, approximations(e.g., rounding, truncating precision, etc.) in beam utilization scores,handover costs, and the like may be employed to bound the solutionspace. In some examples, uncertainty in inputs such as the flight plandata, estimates of beam utilization due to fixed terminals, estimates ofservice utilization for each aircraft, and the like, may be taken intoaccount using stochastic optimization techniques.

FIG. 7 is a block diagram illustrating an example of a beam handovermanager 125-a for satellite beam handover based on predicted networkconditions, in accordance with various aspects of the presentdisclosure. The beam handover manager 125-a may be an example of thebeam handover manager 125 described with reference to FIG. 1 . The beamhandover manager 125-a may include a shared link interface 710,selection trigger detector 720, candidate satellite beam assigner 730,beam utilization score calculator 740, beam utilization criteriaevaluator 750, optimization manager 760, aircraft flexibility manager770, and handover scheduler 780. Each of these components may becommunicatively coupled to each other.

Shared link interface 710 may receive information such as flight plandata, flight status data, network resource data, satellite data, etc.Shared link interface 710 may also forward beam handover data receivedfrom handover scheduler 780. Shared link interface 710 may forward someor all of this data to selection trigger detector 720, candidatesatellite beam assigner 730, and aircraft flexibility manager 770.Selection trigger detector 720 may send a trigger to candidate satellitebeam assigner 730 to select satellite beams for providing network accessservice to one or more aircraft 130 over a service timeframe. Theinstances that cause selection trigger detector 720 to send a triggermay be periodic or may happen under circumstances that are describedabove (e.g., an aircraft being within a certain distance of a beam edge,an aircraft entering a new beam, beam utilization of a beam exceeding athreshold, a number of aircraft serviced by a satellite beam exceedingan aircraft threshold, a number of users of a satellite beam exceeding auser threshold, a difference of beam utilization between two or moresatellite beams exceed a beam delta threshold, etc.).

Candidate satellite beam assigner 730 may first provisionally assignaircraft 130 to candidate satellite beams based on default rules. Beamutilization score calculator 740 may calculate a beam utilization scorefor each candidate satellite beam determined by candidate satellite beamassigner 730. The beam utilization score may be determined by a varietyof factors as described above. Beam utilization criteria evaluator 750may evaluate whether one or more beam utilization scores determined bybeam utilization score calculator 740 meets one or more beam utilizationcriteria as described above. The criteria may include a predeterminedbeam utilization threshold where beam utilization criteria evaluator 750determines if one or more beam utilization scores exceed thepredetermined threshold. The determination may occur over a portion orthe entirety of a service timeframe.

Optimization manager 760 may apply a number of optimization techniquestowards the assigned set of candidate satellite beams in the instancewhere the beam utilization criteria evaluator 750 determines that theset of candidate satellite beams fails to meet the beam utilizationcriteria. One technique may include randomly assigning one or moreaircraft 130 to different candidate satellite beams than they wereassigned in the initial assignment. In another technique, optimizationmanager may receive aircraft flexibility information from aircraftflexibility manager 770 that indicates which aircraft associated with asatellite beam has the highest flexibility in being assigned to anothercandidate satellite beam. Once an optimization technique has beenapplied, candidate satellite beam assigner 730 may receive the resultinginformation. Additionally or alternatively, optimization manager 760 mayemploy optimization techniques using a value function as described aboveincluding Monte Carlo tree search, branch and bound techniques, ordynamic programming.

Handover scheduler 780 may schedule handovers of each aircraft to aselected set of candidate satellite beams during the service timeframebased on the determinations for beam utilization criteria of beamutilization criteria evaluator 750 or optimization results ofoptimization manager 760.

FIG. 8 is a block diagram illustrating an example of a gateway 115-a forsatellite beam handover based on predicted network conditions, inaccordance with various aspects of the present disclosure. The gateway115-a may be an example of the gateway 115 described with reference toFIG. 1 . The gateway 115-a may include a transceiver 810, communicationsinterface 820, beam handover manager 125-b, processor 830, memory 840,software code 845, and bus 850.

Transceiver 810 manages communications between the multi-user accessterminal 170-b and satellite(s) 105 via ground station antenna system110-a. The transceiver 810 may communicate bi-directionally, via one ormore antennas, as described above. The transceiver 810 may also includea modem to modulate the packets and provide the modulated packets to theantennas for transmission, and to demodulate packets received from theantennas. In some examples, a transmitter may be collocated with areceiver in the transceiver 810. Transceiver 810 may be configured tocommunicate with satellite(s) 105 over one or more frequency bands(e.g., Ka, Ku, etc.) and may be configured to automatically orientantenna 110-a to transmit signals to and receive signals fromsatellite(s) 105.

Communications interface module 820 controls network traffic to and fromnetwork 120-a. Communications interface 820 may implement wired networkinterfaces (e.g., Ethernet, Fibre Channel, etc.) and/or wireless networkinterfaces (e.g., IEEE 802.11 compliant interfaces, etc.).

Processor 830 may include an intelligent hardware device, e.g., acentral processing unit (CPU), a microcontroller, an ASIC, etc.Processor 830 may process information received through modem 810 orcommunications interface 820, or information to be sent tocommunications interface 820 or modem 810 for transmission. Processor830 may handle, alone or in connection with gateway 115-a, variousaspects of allocating satellite capacity based on aircraft loadforecasting.

Memory 840 may include random access memory (RAM) or read-only memory(ROM). Memory 840 may store computer-readable, computer-executable code845 containing instructions that are configured to, when executed, causeprocessor 830 to perform various functions described herein.Alternatively, the code 845 may not be directly executable by processor830 but be configured to cause the gateway 115-a (e.g., when compiledand executed) to perform various of the functions described herein.

Beam handover manager 125-b may, in conjunction with memory 840 andprocessor 830, perform the functions described above includingperforming satellite beam handover based on predicted networkconditions. For example, beam handover manager 125-b may calculate beamutilization scores of candidate satellite beams for providing networkservice for aircraft over one or more service timeframes based onpredicted beam utilization. Based on the beam utilization scores, beamhandover manager 125-b may select satellite beams to provide networkservice for each aircraft. Beam handover manager 125-b may then schedulea handover of network service for each aircraft to the selectedsatellite beams and may subsequently reselect satellite beams forcertain aircraft based on changing network conditions.

The components of the gateway 115-a may, individually or collectively,be implemented with one or more application-specific integrated circuits(ASICs) adapted to perform some or all of the applicable functions inhardware. Alternatively, the functions may be performed by one or moreother processing units (or cores), on one or more integrated circuits.In other embodiments, other types of integrated circuits may be used(e.g., Structured/Platform ASICs, Field Programmable Gate Arrays(FPGAs), and other Semi-Custom ICs), which may be programmed in anymanner known in the art. The functions of each unit may also beimplemented, in whole or in part, with instructions embodied in amemory, formatted to be executed by one or more general orapplication-specific processors.

FIG. 9 is a flowchart diagram of an example method 900 for performingsatellite beam handover based on predicted network conditions. Method900 may be performed, for example, by the beam handover manager 125 ofFIGS. 1, 7, and 8 .

At block 905 of method 900, beam handover manager 125 receives flightplan data for one or more aircraft that are provided network accessservice via the multi-beam satellite system and forecasts travel pathsfor the one or more aircraft. Beam handover manager 125 may receive thisflight plan data via network 120 or it may receive the data from theaircraft 130 (e.g., via satellite 105).

With the flight plan data, beam handover manager 125 identifies, foreach aircraft 130, respective candidate satellite beams for providingthe network access service (e.g., successively) over a service timeframeat block 910. At block 915, beam handover manager 125 may obtain, foreach of the satellite beams for a service timeframe, a beam utilizationscore indicative of predicted beam utilization over the servicetimeframe. The beam utilization score of each candidate satellite beammay be based on a plurality of beam utilization factors comprising oneor more of empirical beam utilization data, a number of fixed terminalsserviced by each of the plurality of satellite beams, provisionedservice levels for the fixed terminals, historical beam utilizationdata, an estimated number of the passengers utilizing the network accessservice on each aircraft, a service level offered to the passengersutilizing the network access service on each aircraft. The beamutilization scores may also be a weighted sum of the plurality of beamutilization factors.

At block 920 beam handover manager 125 selects, over the servicetimeframe, satellite beams for providing the network access service foreach aircraft of the plurality of aircraft based in part on the beamutilization scores for the respective candidate satellite beams. In someexamples, the selecting may be based on an estimated service utilizationassociated with each aircraft relative to the beam utilization scoresfor the respective candidate satellite beams. In some examples, theselecting may be based on a cost of utilization of each of therespective candidate satellite beams, minimizing a number of satellitebeam handovers for the plurality of aircraft, minimizing handovers to asatellite beam of a satellite different from the satellite currentlyserving an aircraft, or a combination thereof. In some examples, theselecting may be based on receiving a handover evaluation trigger wherethe trigger may be one or more of a periodic trigger, detecting anaircraft within a certain distance from an edge of a satellite beamcurrently serving the aircraft, detecting an aircraft entering into anoverlapping region of multiple satellite beams, beam utilization of asatellite beam of the plurality of satellite beams exceeding a capacitythreshold, a number of aircraft serviced by a satellite beam of theplurality of satellite beams exceeding an aircraft threshold, a numberof users of a satellite beam of the plurality of satellite beamsexceeding a user threshold, a change in the flight plan data, detectinga difference of beam utilization between two or more satellite beamsexceeding a beam delta threshold, or a service level of the networkaccess service to an aircraft falling below a service threshold.

Method 900 then proceeds to block 925, where beam handover manager 125schedules at least one handover for at least one of the plurality ofaircraft to a selected satellite beam during the service timeframe. Atblock 930, method 900 may continue to another example that will bedescribed in FIG. 10 .

FIG. 10 is a flowchart diagram of an example method 1000 for performingsatellite beam handover based on predicted network conditions. Method1000 may be an example method for implementing aspects of method 900.Method 1000 may be performed, for example, by the beam handover manager125 of FIGS. 1, 7, and 8 .

Method 1000 may after block 910 of FIG. 9 , where respective candidatesatellite beams for providing network access service to a plurality ofaircraft have been identified. At block 1005, beam handover manager 125provisionally selects, for each of the plurality of aircraft, arespective set of candidate satellite beams for providing the networkaccess service during the service timeframe. The provisional selectionsmay be based, for example, on default rules for beam assignment. Withthe provisional selections of the candidate satellite beams, beamhandover manager 125 updates the beam utilization score for therespective sets of candidate satellite beams based on an estimatedservice utilization of each beam associated with each aircraft duringthe service timeframe at block 1010. At block 1015, beam handovermanager 125 determines whether a beam utilization score for at least oneof the plurality of satellite beams does not meet a beam utilizationcriteria during the service timeframe. If, at block 1015, beam handovermanager 125 determines that the satellite beams have beam utilizationscores that meet a beam utilization criteria during the servicetimeframe, method 1000 terminates and returns to block 925 forscheduling of handovers during the service timeframe based on the beamassignments. If, at block 1015, beam handover manager 125 determinesthat at least one satellite beam has a beam utilization score that doesnot meet a beam utilization criteria during the service timeframe,method 1000 proceeds to block 1020.

At block 1020, beam handover manager 125 identifies aircraft that arebeing serviced by the at least one of the plurality of satellite beamsfor which the beam utilization score does not meet a beam utilizationcriteria during the service timeframe. For the identified aircraft, beamhandover manager 125 may exchange the satellite beams having beamutilization scores that do not meet the beam utilization criteria forsubstitute satellite beams. In one example, beam handover manager 125creates a ranked list of the identified aircraft based on a beamflexibility metric associated with each of the identified aircraft atblock 1025. The beam flexibility metric may be based on the number ofavailable satellite beams for the each of the identified aircraft duringthe associated service timeframe. Utilizing the ranked list, beamhandover manager 125 re-selects a different one of the respectivecandidate satellite beams for providing the network access service atblock 1030. Method 1000 then returns to block 1010 to update the beamutilization scores for the candidate satellite beams based on there-assignments of aircraft to candidate satellite beams at block 1030.

It should be noted that these methods describe possible implementations,and that the operations and the steps may be rearranged or otherwisemodified such that other implementations are possible. In some examples,aspects from two or more of the methods may be combined. For example,aspects of each of the methods may include steps or aspects of the othermethods, or other steps or techniques described herein. Thus, aspects ofthe disclosure may provide for consumer preference and maintenanceinterface.

The description herein is provided to enable a person skilled in the artto make or use the disclosure. Various modifications to the disclosurewill be readily apparent to those skilled in the art, and the genericprinciples defined herein may be applied to other variations withoutdeparting from the scope of the disclosure. Thus, the disclosure is notto be limited to the examples and designs described herein but is to beaccorded the broadest scope consistent with the principles and novelfeatures disclosed herein.

The functions described herein may be implemented in hardware, softwareexecuted by a processor, firmware, or any combination thereof. Ifimplemented in software executed by a processor, the functions may bestored on or transmitted over as one or more instructions or code on acomputer-readable medium. Other examples and implementations are withinthe scope of the disclosure and appended claims. For example, due to thenature of software, functions described herein can be implemented usingsoftware executed by a processor, hardware, firmware, hardwiring, orcombinations of any of these. Features implementing functions may alsobe physically located at various positions, including being distributedsuch that portions of functions are implemented at different physicallocations. Also, as used herein, including in the claims, “or” as usedin a list of items (for example, a list of items prefaced by a phrasesuch as “at least one of” or “one or more”) indicates an inclusive listsuch that, for example, a list of at least one of A, B, or C means A orB or C or AB or AC or BC or ABC (i.e., A and B and C).

Computer-readable media includes both non-transitory computer storagemedia and communication media including any medium that facilitatestransfer of a computer program from one place to another. Anon-transitory storage medium may be any available medium that can beaccessed by a general purpose or special purpose computer. By way ofexample, and not limitation, non-transitory computer-readable media cancomprise RAM, ROM, electrically erasable programmable read only memory(EEPROM), compact disk (CD) ROM or other optical disk storage, magneticdisk storage or other magnetic storage devices, or any othernon-transitory medium that can be used to carry or store desired programcode means in the form of instructions or data structures and that canbe accessed by a general-purpose or special-purpose computer, or ageneral-purpose or special-purpose processor. Also, any connection isproperly termed a computer-readable medium. For example, if the softwareis transmitted from a website, server, or other remote source using acoaxial cable, fiber optic cable, twisted pair, digital subscriber line(DSL), or wireless technologies such as infrared, radio, and microwave,then the coaxial cable, fiber optic cable, twisted pair, DSL, orwireless technologies such as infrared, radio, and microwave areincluded in the definition of medium. Disk and disc, as used herein,include CD, laser disc, optical disc, digital versatile disc (DVD),floppy disk and Blu-ray disc where disks usually reproduce datamagnetically, while discs reproduce data optically with lasers.Combinations of the above are also included within the scope ofcomputer-readable media.

The various illustrative blocks and modules described in connection withthe disclosure herein may be implemented or performed with ageneral-purpose processor, a digital signal processor (DSP), an ASIC, anfield programmable gate array (FPGA) or other programmable logic device,discrete gate or transistor logic, discrete hardware components, or anycombination thereof designed to perform the functions described herein.A general-purpose processor may be a microprocessor, but in thealternative, the processor may be any conventional processor,controller, microcontroller, or state machine. A processor may also beimplemented as a combination of computing devices (e.g., a combinationof a DSP and a microprocessor, multiple microprocessors, one or moremicroprocessors in conjunction with a DSP core, or any other suchconfiguration). The functions of each unit may also be implemented, inwhole or in part, with instructions embodied in a memory, formatted tobe executed by one or more general or application-specific processors.

In the appended figures, similar components or features may have thesame reference label. Further, various components of the same type maybe distinguished by following the reference label by a dash and a secondlabel that distinguishes among the similar components. If just the firstreference label is used in the specification, the description isapplicable to any one of the similar components having the same firstreference label irrespective of the second reference label.

What is claimed is:
 1. A method for satellite management for aircraft ina satellite communication system comprising a plurality of satellitebeams, the method comprising: identifying a plurality of aircraft beingprovided network access service for passengers via the satellitecommunication system; assigning at least one satellite beam of theplurality of satellite beams to each aircraft of the plurality ofaircraft; determining that at least one resource criteria associatedwith at least one satellite beam of the plurality of satellite beams isno longer satisfied; and reallocating a beam resource of the satellitecommunication system based at least in part on the determination,wherein the reallocating comprises: provisionally selecting, for one ormore of the plurality of aircraft, one or more respective candidatesatellite beams for providing the network access service based at leastin part on reallocating the beam resource; iteratively performing theprovisionally selecting until the at least one resource criteria issatisfied; and adopting the provisionally selected one or morerespective candidate satellite beams for the one or more of theplurality of aircraft.
 2. The method of claim 1, wherein thereallocating comprises: exchanging a satellite beam assigned to arespective aircraft for a substitute satellite beam satisfying the atleast one resource criteria.
 3. A method for satellite management foraircraft in a satellite communication system comprising a plurality ofsatellite beams, the method comprising: identifying a plurality ofaircraft being provided network access service for passengers via thesatellite communication system; assigning at least one satellite beam ofthe plurality of satellite beams to each aircraft of the plurality ofaircraft; determining that at least one resource criteria associatedwith at least one satellite beam of the plurality of satellite beams isno longer satisfied; and reallocating a beam resource of the satellitecommunication system based at least in part on the determination,wherein the reallocating is further based at least in part on one ormore priority rules.
 4. The method of claim 3, wherein the one or morepriority rules comprise a priority based on a satellite technology, apriority based on a satellite operator, a priority based on linkperformance, or a combination thereof.
 5. The method of claim 1, whereinthe beam resource is a beam frequency, a beam polarization, a beamstrength, time resources of a beam, or a combination thereof.
 6. Themethod of claim 1, further comprising: detecting that an aircraft iswithin a threshold distance from an edge of a satellite beam currentlyserving the aircraft or that the aircraft has entered into anoverlapping region of multiple satellite beams, wherein the determiningis based at least in part on the detecting.
 7. The method of claim 1,wherein the at least one resource criteria is a number of aircraftserviced by a satellite beam.
 8. The method of claim 1, wherein the atleast one resource criteria is a beam utilization of a satellite beam, anumber of users serviced by a satellite beam, a change in capacitydemand for one or more satellite beams, a difference of beam utilizationbetween two or more satellite beams, a service level of the networkaccess service to an aircraft, or a combination thereof.
 9. The methodof claim 1, wherein the plurality of satellite beams are provided via aplurality of satellites.
 10. An apparatus for satellite management foraircraft in a satellite communication system comprising a plurality ofsatellite beams, comprising: a processor; memory coupled with theprocessor; and instructions stored in the memory; wherein theinstructions are executable by the processor to cause the apparatus to:identify a plurality of aircraft being provided network access servicefor passengers via the satellite communication system; assign at leastone satellite beam of the plurality of satellite beams to each aircraftof the plurality of aircraft; determine that at least one resourcecriteria associated with at least one satellite beam of the plurality ofsatellite beams is no longer satisfied; and reallocate a beam resourceof the satellite communication system based at least in part on thedetermination, wherein, to reallocate the beam resource, theinstructions are executable by the processor to cause the apparatus to:provisionally select, for one or more of the plurality of aircraft, oneor more respective candidate satellite beams for providing the networkaccess service based at least in part on reallocating the beam resource;iteratively perform the provisionally selecting until the at least oneresource criteria is satisfied; and adopt the provisionally selected oneor more respective candidate satellite beams for the one or more of theplurality of aircraft.
 11. The apparatus of claim 10, wherein theinstructions for reallocating are further executable by the processor tocause the apparatus to: exchange a satellite beam assigned to arespective aircraft for a substitute satellite beam satisfying the atleast one resource criteria.
 12. An apparatus for satellite managementfor aircraft in a satellite communication system comprising a pluralityof satellite beams, comprising: a processor; memory coupled with theprocessor; and instructions stored in the memory; wherein theinstructions are executable by the processor to cause the apparatus to:identify a plurality of aircraft being provided network access servicefor passengers via the satellite communication system; assign at leastone satellite beam of the plurality of satellite beams to each aircraftof the plurality of aircraft; determine that at least one resourcecriteria associated with at least one satellite beam of the plurality ofsatellite beams is no longer satisfied; and reallocate a beam resourceof the satellite communication system based at least in part on thedetermination, wherein the reallocating is further based at least inpart on one or more priority rules.
 13. The apparatus of claim 12,wherein the one or more priority rules comprise a priority based on asatellite technology, a priority based on a satellite operator, apriority based on link performance, or a combination thereof.
 14. Theapparatus of claim 10, wherein the beam resource is a beam frequency, abeam polarization, a beam strength, time resources of a beam, or acombination thereof.
 15. The apparatus of claim 10, wherein theinstructions are further executable by the processor to cause theapparatus to: detect that an aircraft is within a threshold distancefrom an edge of a satellite beam currently serving the aircraft or thatthe aircraft has entered into an overlapping region of multiplesatellite beams, wherein the determining is based at least in part onthe detecting.
 16. The apparatus of claim 10, wherein the at least oneresource criteria is a number of aircraft serviced by a satellite beam.17. The apparatus of claim 10, wherein the at least one resourcecriteria is a beam utilization of a satellite beam, a number of usersserviced by a satellite beam, a change in capacity demand for one ormore satellite beams, a difference of beam utilization between two ormore satellite beams, a service level of the network access service toan aircraft, or a combination thereof.
 18. The apparatus of claim 10,wherein the plurality of satellite beams are provided via a plurality ofsatellites.